Virtual notifications

ABSTRACT

One embodiment provides a method, including: detecting, at an electronic device, data; repurposing, using a processor, an output based on the data; and providing, using an output device of the electronic device, the repurposed output as a notification. Other embodiments are described and claimed.

BACKGROUND

Information handling devices (“devices” or “electronic devices”), forexample laptop computers, smart phones, tablet devices, smart watchesand wearables, and the like, are utilized for communicating,calendaring, to make purchases, and in many other daily tasks. Usersoften set or receive notifications, e.g., for events. For example,devices detect an event, e.g., a calendar appointment that has come due,an incoming text message, etc., and provide a notification, alert orreminder for the event (“notification,” “alert,” and “reminder” are usedinterchangeably herein). Common examples include notifications for voicecalls, text messages, instant messages, in-application messages, videocalls, etc. Such devices also provide the user with notificationsregarding events such as scheduled reminders, alarms, etc.

Notifications typically are provided to the device user in the form of avisual display. For example, many smart phones include a tray or screenarea in which notifications (e.g., of received text messages, missedcalls, etc.) are displayed. Different modes of notification, however,may used to provide a notification. For example, a device may provideaudible notifications, on-screen notifications, other visiblenotifications, haptic notifications such as device vibrations, etc.,alone or in some combination.

BRIEF SUMMARY

In summary, one aspect provides a method, comprising: detecting, at anelectronic device, data; repurposing, using a processor, an output basedon the data; and providing, using an output device of the electronicdevice, the repurposed output as a notification.

Another aspect provides a method, comprising: detecting, using aprocessor of an electronic device, an event; displaying a notificationfor the event; identifying, using the processor, data indicating thatthe event has occurred, wherein said data is not obtained from userinput at the electronic device; and automatically clearing thenotification based on the data.

Another aspect provides an apparatus, comprising: an output device; aprocessor operatively coupled to the output device; and a memory thatstores instructions executable by the processor to: detect data;repurpose an output based on the data; and provide, using the outputdevice, the repurposed output as a notification.

A further aspect provides a program product, comprising: a computerreadable storage device comprising code executable by a processor, thecode comprising: code that detects, at an electronic device, data; codethat repurposes, using a processor, an output based on the data; andcode that provides, using an output device of the electronic device, therepurposed output as a notification.

The foregoing is a summary and thus may contain simplifications,generalizations, and omissions of detail; consequently, those skilled inthe art will appreciate that the summary is illustrative only and is notintended to be in any way limiting.

For a better understanding of the embodiments, together with other andfurther features and advantages thereof, reference is made to thefollowing description, taken in conjunction with the accompanyingdrawings. The scope of the invention will be pointed out in the appendedclaims.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

FIG. 1 illustrates an example of information handling device circuitry.

FIG. 2 illustrates another example of information handling devicecircuitry.

FIG. 3 illustrates an example method of setting a virtual notificationthat is modified over time.

FIG. 4 illustrates an example method of implementing a virtualnotification.

FIG. 5 illustrates another example method of implementing a virtualnotification.

FIG. 6 illustrates an example method of automatically clearing anotification.

DETAILED DESCRIPTION

It will be readily understood that the components of the embodiments, asgenerally described and illustrated in the figures herein, may bearranged and designed in a wide variety of different configurations inaddition to the described example embodiments. Thus, the following moredetailed description of the example embodiments, as represented in thefigures, is not intended to limit the scope of the embodiments, asclaimed, but is merely representative of example embodiments.

Reference throughout this specification to “one embodiment” or “anembodiment” (or the like) means that a particular feature, structure, orcharacteristic described in connection with the embodiment is includedin at least one embodiment. Thus, the appearance of the phrases “in oneembodiment” or “in an embodiment” or the like in various placesthroughout this specification are not necessarily all referring to thesame embodiment.

Furthermore, the described features, structures, or characteristics maybe combined in any suitable manner in one or more embodiments. In thefollowing description, numerous specific details are provided to give athorough understanding of embodiments. One skilled in the relevant artwill recognize, however, that the various embodiments can be practicedwithout one or more of the specific details, or with other methods,components, materials, et cetera. In other instances, well knownstructures, materials, or operations are not shown or described indetail to avoid obfuscation.

While many notification types exist, a user must deal with conventionalnotifications or let the notification tray or area get unwieldy.Clearing a notification to make it go away also sometimes causes theuser to forget about the notification. Furthermore, notifications mustbe cleared or acknowledged manually, even if the event associated withthe notification has taken place.

An embodiment therefore provides for virtual notifications that alertthe user of something in a different way than conventionalnotifications. For example, a conventional notification may take theform of a point-in-time visual notification, e.g., a pop up display oftext contained within a notification window, which the user has to keeptrack of and defer or cancel. In contrast, an embodiment insteadprovides a soft or virtual notification that utilizes a repurposedoutput, such as a display screen background color that is changed toprovide a notification, a background color on a sub-portion of thedisplay screen that is changed (e.g., a task tray or notification bar),a color surrounding an application or application icon that is changed,a change to a home screen application icon or badge, a relocation of anapplication icon or badge (within a screen or between screens), etc., asthe notification. This virtual notification can become active in any orall of the user's devices.

According to an embodiment, a virtual notification doesn't have toalways show up or always persist. For example, a virtual notificationmay only be implemented or displayed at certain times, such as when theuser is using a particular device, or when the user is at a particularlocation (geographic location or virtual location, such as a web site),or at particular times when the user will be near or at a particularlocation (e.g., grocery store, web site, device application, etc.).

In an embodiment, a notification may be automatically cleared, e.g.,based on a policy. For example, an embodiment may use data (e.g., datathat is sensed, such as location data, data that is external to thedevice, such as purchasing or transactional data, data that is availableto a device application, such as browser history data, etc.) todetermine that the event or task for which a notification is created hasbeen addressed or completed by the user.

The illustrated example embodiments will be best understood by referenceto the figures. The following description is intended only by way ofexample, and simply illustrates certain example embodiments.

While various other circuits, circuitry or components may be utilized ininformation handling devices, with regard to smart phone and/or tabletcircuitry 100, an example illustrated in FIG. 1 includes a system on achip design found for example in tablet or other mobile computingplatforms. Software and processor(s) are combined in a single chip 110.Processors comprise internal arithmetic units, registers, cache memory,busses, I/O ports, etc., as is well known in the art. Internal bussesand the like depend on different vendors, but essentially all theperipheral devices (120) may attach to a single chip 110. The circuitry100 combines the processor, memory control, and I/O controller hub allinto a single chip 110. Also, systems 100 of this type do not typicallyuse SATA or PCI or LPC. Common interfaces, for example, include SDIO andI2C.

There are power management chip(s) 130, e.g., a battery management unit,BMU, which manage power as supplied, for example, via a rechargeablebattery 140, which may be recharged by a connection to a power source(not shown). In at least one design, a single chip, such as 110, is usedto supply BIOS like functionality and DRAM memory.

System 100 typically includes one or more of a WWAN transceiver 150 anda WLAN transceiver 160 for connecting to various networks, such astelecommunications networks and wireless Internet devices, e.g., accesspoints. Additional devices 120 are commonly included, e.g., a shortrange wireless device for communicating with other devices. System 100often includes a touch screen 170 for data input and display/rendering.System 100 also typically includes various memory devices, for exampleflash memory 180 and SDRAM 190.

FIG. 2 depicts a block diagram of another example of informationhandling device circuits, circuitry or components. The example depictedin FIG. 2 may correspond to computing systems such as the THINKPADseries of personal computers sold by Lenovo (US) Inc. of Morrisville,N.C., or other devices. As is apparent from the description herein,embodiments may include other features or only some of the features ofthe example illustrated in FIG. 2.

The example of FIG. 2 includes a so-called chipset 210 (a group ofintegrated circuits, or chips, that work together, chipsets) with anarchitecture that may vary depending on manufacturer (for example,INTEL, AMD, ARM, etc.). INTEL is a registered trademark of IntelCorporation in the United States and other countries. AMD is aregistered trademark of Advanced Micro Devices, Inc. in the UnitedStates and other countries. ARM is an unregistered trademark of ARMHoldings plc in the United States and other countries. The architectureof the chipset 210 includes a core and memory control group 220 and anI/O controller hub 250 that exchanges information (for example, data,signals, commands, etc.) via a direct management interface (DMI) 242 ora link controller 244. In FIG. 2, the DMI 242 is a chip-to-chipinterface (sometimes referred to as being a link between a “northbridge”and a “southbridge”). The core and memory control group 220 include oneor more processors 222 (for example, single or multi-core) and a memorycontroller hub 226 that exchange information via a front side bus (FSB)224; noting that components of the group 220 may be integrated in a chipthat supplants the conventional “northbridge” style architecture. One ormore processors 222 comprise internal arithmetic units, registers, cachememory, busses, I/O ports, etc., as is well known in the art.

In FIG. 2, the memory controller hub 226 interfaces with memory 240 (forexample, to provide support for a type of RAM that may be referred to as“system memory” or “memory”). The memory controller hub 226 furtherincludes a low voltage differential signaling (LVDS) interface 232 for adisplay device 292 (for example, a CRT, a flat panel, touch screen,etc.). A block 238 includes some technologies that may be supported viathe LVDS interface 232 (for example, serial digital video, HDMI/DVI,display port). The memory controller hub 226 also includes a PCI-expressinterface (PCI-E) 234 that may support discrete graphics 236.

In FIG. 2, the I/O hub controller 250 includes a SATA interface 251 (forexample, for HDDs, SDDs, etc., 280), a PCI-E interface 252 (for example,for wireless connections 282), a USB interface 253 (for example, fordevices 284 such as a digitizer, keyboard, mice, cameras, phones,microphones, storage, other connected devices, etc.), a networkinterface 254 (for example, LAN), a GPIO interface 255, a LPC interface270 (for ASICs 271, a TPM 272, a super I/O 273, a firmware hub 274, BIOSsupport 275 as well as various types of memory 276 such as ROM 277,Flash 278, and NVRAM 279), a power management interface 261, a clockgenerator interface 262, an audio interface 263 (for example, forspeakers 294), a TCO interface 264, a system management bus interface265, and SPI Flash 266, which can include BIOS 268 and boot code 290.The I/O hub controller 250 may include gigabit Ethernet support.

The system, upon power on, may be configured to execute boot code 290for the BIOS 268, as stored within the SPI Flash 266, and thereafterprocesses data under the control of one or more operating systems andapplication software (for example, stored in system memory 240). Anoperating system may be stored in any of a variety of locations andaccessed, for example, according to instructions of the BIOS 268. Asdescribed herein, a device may include fewer or more features than shownin the system of FIG. 2.

Information handling device circuitry, as for example outlined in FIG. 1or FIG. 2, may be used in devices that provide notifications to users.The notifications comprise indications that an event has occurred orwill occur. For example, a notification may be provided in response toan event, e.g., a message that has been received by a device. As anotherexample, a notification may be provided that another type of event hasoccurred, e.g., it is 15 minutes before a calendar appointment willoccur or a reminder comes due.

The virtual notifications described herein may take a variety of formsand may be provided in a variety of ways. In the non-limiting examplesused herein, a displayed virtual notification is used. However, it willbe readily apparent that other virtual notifications, for exampleaudible notifications, haptic notifications, etc., may be employedinstead of or in addition to a displayed virtual notification, asdetermined for example from the use context, the user's preferences, thedevice capabilities, etc.

Illustrated in FIG. 3 is an example of providing a virtual notificationthat alerts or reminds a user of an event. At 301, an event is detected.For example, a user may request that a virtual assistant place an itemin a wish list such that the user is reminded to purchase the itemlater, e.g., in a week. Therefore, in this particular example, the eventis the creation of a reminder for purchasing the item in one week.

A standard notification or alert in this use context might be a pop uptext notification window that is displayed at a set time, e.g., one dayprior to the end of the week time period. As is conventionally known,the user must acknowledge and cancel or defer this type of conventionalnotification.

Thus, an embodiment instead identifies a virtual notification that maybe used, as illustrated at 302, for notifying the user of the event. Inan embodiment, an output such as display screen color, application iconor graphic size and/or location, etc., may be modified or repurposed foruse as a virtual notification.

For example, an embodiment identifies a notification, such as abackground color for a display screen (or portion thereof), to use as avirtual notification for the event at 302. This identification mayproceed according to a setting chosen by the user or according to adefault setting. For example, at 302 an embodiment may identify that avirtual notification option has been selected by the user. Of course, ifno such virtual notification setting is indicated, a defaultnotification may be used, e.g., popup text window.

When a virtual notification has been identified, e.g., a user hasenabled the use of a displayed color as a virtual notification; it maybe displayed on the display device for the user, as illustrated at 304.

By way of specific example, in an embodiment the virtual notificationmay utilize colors in a variety of ways. For example, a red backgroundcolor for a notification bar may indicate charging the device's batteryis needed or recommended, a green background color for the notificationbar may be used as a reminder to buy an item, as per the non-limitingexample used above, a yellow background color for the notification barmay indicate that a reminder has been set to stop at a particularlocation on the way home from work, etc. Therefore, an embodiment maymodify an output, e.g., repurpose the default color of the notificationbar to a new color as the virtual notification, as illustrated at 303.

In an embodiment, the virtual notification may be modified over time.Thus, an embodiment may determine a modification of the virtualnotification, as illustrated at 305. For example, as a virtualnotification may be a background color on the home screen, a change to aparticular home screen application icon or badge, a temporary relocationof an application icon or badge, etc. A modification may include a rateat which the background color changes, an amount by which the size of anapplication icon changes, a particular location to which an applicationicon is to relocated, etc.

When a modification to an output has been determined at 303, a virtualnotification that is displayed, as illustrated at 304, may be modifiedaccording to the time based modification, as illustrated at 305. By wayof specific example, if the virtual notification identified comprises acolor change to the background color of a device's notification bar,e.g., to remind the user to purchase an item by week's end, thenotification bar itself may change color over time to indicate a task, ato-do item, an upcoming event, etc., is approaching. In contrast,conventionally a device's notification bar is always a static color, andthis static color is non-function, i.e., it is not linked to anynotification, reminder or alert. In an embodiment, the initial virtualnotification displayed at 304 may be a neutral color, e.g., grey,whereas a modified virtual notification displayed at 305 may be red,e.g., to indicate that an upcoming event, here a purchase of an itemwithin a week's time, is drawing nearer in time. Similarly, a change incolor may be a change to the intensity of the color, the transparency ofthe color, etc.

An embodiment may identify a virtual reminder at 302 in response todetermining that a default/conventional notification has been set. Forexample, a default/conventional notification may be supplemented by ortransitioned into a virtual notification. By way of example, if a userinputs default/conventional reminders for an event at one day before,four hours before, one hour before, and fifteen minutes before acalendar appointment, an embodiment may implement a single virtualnotification instead of or in addition to the separatedefault/conventional notifications leading up to the event. The virtualreminder may be a single, persistent virtual reminder that does notchange, or, the virtual reminder may be one that is modified over time.For example, an embodiment may implement a virtual reminder that hasmultiple tiers that track the progression of the default/conventionalreminders. Thus, if the virtual reminder displayed at 304 is abackground color, the background color may be modified at 305 repeatedlyto change the background color to from semi-transparent red at one daybefore the event to a darker, more opaque red background color as theevent time approaches, e.g., one color or transparency change perstandard reminder time increment.

The virtual notification(s) can become active and be displayed by orprovided by any or all of the user's devices. For example, a virtualnotification generated by a user's laptop or smart phone may appear on auser's smart watch or other linked device.

In an embodiment, as illustrated in FIG. 4, a virtual notification maybe provided in the form of a relocated display element. Therefore, if anevent is detected at 401, e.g., an in-application message is received ina smart phone application; an embodiment may identify a notification forthe event at 402. For example, in lieu of or in addition to a defaultnotification, such as a text notification provided in a status bar, aflashing light in a display bezel, the appearance of a number on theapplication's icon or badge, etc., an embodiment may identify a virtualnotification in the form of relocating a display element, as illustratedat 403. By way of specific example, an embodiment may determine at 403that the application's icon is to be relocated within the display, e.g.,to place it in a more prominent or noticeable position within a displayview. This is the digital equivalent of putting an item in your house soyou have to step over it until you finally deal with it or put it away.Thus, the virtual notification may be implemented in the form ofrelocating the display element, e.g., an application icon, within thedisplay, as illustrated at 404.

Another example of implementing a virtual reminder is illustrated inFIG. 5. Here, a virtual notification may be provided in the form of achange in the size of display element. Therefore, if an event isdetected at 501, e.g., a social media application status update isreceived in a smart phone application, an embodiment may identify anotification for the event at 502. For example, in lieu of or inaddition to a default notification, such as a text notification providedin a status bar, a flashing light in a display bezel, etc., anembodiment may identify a virtual notification in the form of a sizechange to a display element at 503. For example, an embodiment maydetermine at 503 that the application's icon is to be changed in size,e.g., to increase it's size such that it is more prominent ornoticeable. Thus, the virtual notification may be implemented in theform of increasing the size of the display element, e.g., an applicationicon, within the display, as illustrated at 504.

Referring to FIG. 6, an embodiment offers improved techniques forclearing of notifications, whether a virtual notification, adefault/conventional notification, or both. In an embodiment, the factthat an event reminder has been set is detected at 601, e.g., a calendarappointment is detected for a particular place and time. An embodimentdetermines if the event for which the reminder or notification is sethas occurred at 602. If not, the reminder or notification may bemaintained. However, if the event has occurred, an embodiment acts toautomatically clear the reminder or notification at 603.

By way of specific example, if a user sets a calendar appointment tomeet with a particular person, at a particular time and place, this isdetected by an embodiment at 601. Thereafter, if data is available thatindicates that the event has occurred, here for example, data indicatingthat the particular person's device is detected via short range wirelesscommunication, data indicating that the user's device is within aparticular meeting room at a particular time, data indicating that theuser's device has called a dial in number for the meeting, etc., anembodiment uses this data to determine that the event has occurred at602 and thereafter an embodiment automatically clears the reminder at603.

Thus, using an embodiment, when a user stops at a required location,buys a required item, visits a particular web site, etc., such data isused to determine that a notification (virtual or conventional) is to beautomatically dismissed. This is in contrast to conventional approaches,which require a user to manually dismiss a notification.

By way of specific example, an embodiment may detect, e.g., via GPSdata, that a user has went to a location associated with a reminderevent. This GPS data (or related data, such as map application data) maythus be utilized by an embodiment to reset or dismiss a virtualnotification for the event associated with the location. Therefore, if auser arrives at the event location, the virtual notification isautomatically dismissed.

Other data sources may be used, e.g., in lieu of or in addition tolocation data. For example, an embodiment may utilize transactional datato determine that a user has made a purchase associated with a reminderevent, e.g., using a credit card or virtual wallet application data.Other sources of transactional data are also available. For example, anexternal purchase (even at a brick and mortar store) may be used todismiss a virtual notification, as credit cards email or send an SMStext message to user's devices, e.g., when buying certain things fromcertain stores. An embodiment may utilize this reported transactionaldata to infer that a task such as purchasing an item on a wish list hastaken place. For example, a user may share purchase history data with ashopping list application or service. Thus, a purchase made for an itemon a shopping list, e.g., with one of the user's credit cards, mayresult in removing the item from the shopping list as well as turningoff or clearing a notification that was set to remind the user to makethe shopping list purchase.

According to an embodiment, a virtual reminder need not always persistor be displayed. Rather, the display or delivery of the virtualnotification may be triggered by various data. For example, if a useradds an item a grocery list, a virtual notification for reminding theuser to purchase that item is not necessarily persistently displayed.Rather, according to an embodiment, the virtual reminder to purchase theitem may be displayed at a particular time, e.g., when the user isdetected at his or her computer, when the user is detected to be locatedat a particular virtual location, e.g., when the user is at a particularweb site. Likewise, the virtual reminder may be displayed on aparticular day where a travel route takes the user near a grocery store,etc. Thus, the virtual reminder may be provided based on various data,e.g., current or future (predicted) location, current device activity oruse context, etc. Therefore, when a user arrives at a certain location,or performs a certain activity, e.g., joins a video conference call, thepresence of that data may trigger presentation of, as well as dismissalof, the virtual notification.

As will be appreciated by one skilled in the art, various aspects may beembodied as a system, method or device program product. Accordingly,aspects may take the form of an entirely hardware embodiment or anembodiment including software that may all generally be referred toherein as a “circuit,” “module” or “system.” Furthermore, aspects maytake the form of a device program product embodied in one or more devicereadable medium(s) having device readable program code embodiedtherewith.

It should be noted that the various functions described herein may beimplemented using instructions stored on a device readable storagemedium such as a non-signal storage device, where the instructions areexecuted by a processor. A storage device may be, for example, anelectronic, magnetic, optical, electromagnetic, infrared, orsemiconductor system, apparatus, or device, or any suitable combinationof the foregoing. More specific examples of a storage medium wouldinclude the following: a portable computer diskette, a hard disk, arandom access memory (RAM), a read-only memory (ROM), an erasableprogrammable read-only memory (EPROM or Flash memory), an optical fiber,a portable compact disc read-only memory (CD-ROM), an optical storagedevice, a magnetic storage device, or any suitable combination of theforegoing. In the context of this document, a storage device is not asignal and “non-transitory” includes all media except signal media.

Program code embodied on a storage medium may be transmitted using anyappropriate medium, including but not limited to wireless, wireline,optical fiber cable, RF, et cetera, or any suitable combination of theforegoing.

Program code for carrying out operations may be written in anycombination of one or more programming languages. The program code mayexecute entirely on a single device, partly on a single device, as astand-alone software package, partly on single device and partly onanother device, or entirely on the other device. In some cases, thedevices may be connected through any type of connection or network,including a local area network (LAN) or a wide area network (WAN), orthe connection may be made through other devices (for example, throughthe Internet using an Internet Service Provider), through wirelessconnections, e.g., near-field communication, or through a hard wireconnection, such as over a USB connection.

Example embodiments are described herein with reference to the figures,which illustrate example methods, devices and program products accordingto various example embodiments. It will be understood that the actionsand functionality may be implemented at least in part by programinstructions. These program instructions may be provided to a processorof a device, a special purpose information handling device, or otherprogrammable data processing device to produce a machine, such that theinstructions, which execute via a processor of the device implement thefunctions/acts specified.

It is worth noting that while specific blocks are used in the figures,and a particular ordering of blocks has been illustrated, these arenon-limiting examples. In certain contexts, two or more blocks may becombined, a block may be split into two or more blocks, or certainblocks may be re-ordered or re-organized as appropriate, as the explicitillustrated examples are used only for descriptive purposes and are notto be construed as limiting.

As used herein, the singular “a” and “an” may be construed as includingthe plural “one or more” unless clearly indicated otherwise.

This disclosure has been presented for purposes of illustration anddescription but is not intended to be exhaustive or limiting. Manymodifications and variations will be apparent to those of ordinary skillin the art. The example embodiments were chosen and described in orderto explain principles and practical application, and to enable others ofordinary skill in the art to understand the disclosure for variousembodiments with various modifications as are suited to the particularuse contemplated.

Thus, although illustrative example embodiments have been describedherein with reference to the accompanying figures, it is to beunderstood that this description is not limiting and that various otherchanges and modifications may be affected therein by one skilled in theart without departing from the scope or spirit of the disclosure.

What is claimed is:
 1. A method, comprising: detecting, at an electronicdevice, data associated with a notification comprising a reminderrelated to a task of a user; modifying, using a processor, an outputbased on the data, wherein the modifying comprises modifying anattribute of the notification based upon the task, wherein the modifyingis based upon a type of the task and a temporal characteristic of thetask; providing, using an output device of the electronic device, themodified output as a notification; and dismissing the notification upondetection of completion of the task, the detection of completion beingbased upon at least one of: a correlation of a location of the user andthe task and transactional data from a source other than the electronicdevice.
 2. The method of claim 1, wherein the providing comprisesincreasing an intensity of the notification over a period of time. 3.The method of claim 2, wherein the increasing progresses according to apolicy.
 4. The method of claim 1, wherein the notification comprises achange to a displayed color.
 5. The method of claim 4, wherein thedisplayed color is displayed on a sub-portion of a display screen. 6.The method of 1, wherein providing of the notification comprisesrelocation of a display screen element.
 7. The method of claim 1,wherein providing of the notification comprises a change in size of adisplay screen element.
 8. The method of claim 1, further comprisingproviding the notification on at least one other user device.
 9. Themethod of claim 1, further comprising: detecting, using a processor ofan electronic device, an event; identifying, using the processor, dataindicating that the event has occurred, wherein said data is notobtained from user input at the electronic device; and automaticallyclearing the notification based on the data indicating that the eventhas occurred.
 10. The method of claim 9, wherein the data is selectedfrom the group consisting of transactional data, web browsing data, andgeographic location data.
 11. The method of claim 9, wherein the data isgeographic location data obtained from a global positioning satellite(GPS) system.
 12. The method of claim 9, wherein the data is time data.13. The method of claim 9, wherein the data is obtained from a remotedevice.
 14. A method, comprising: detecting, using a processor of anelectronic device, an event having an associated time comprising areminder related to a task of a user; displaying a notification for theevent based upon the task; identifying, using the processor, data otherthan time data indicating that the event has occurred, wherein said datais not obtained from user input at the electronic device, wherein theidentifying is based upon a type of the task and a temporalcharacteristic of the task; and dismissing the notification upondetection of completion of the task, the detection of completion beingbased upon at least one of: a correlation of a location of the user andthe task and transactional data from a source other than the electronicdevice.
 15. An apparatus, comprising: an output device; a processoroperatively coupled to the output device; and a memory that storesinstructions executable by the processor to: detect data associated witha notification comprising a reminder related to a task of a user; modifyan output based on the data, wherein to modify comprises to modify anattribute of the notification based upon the task, wherein to modify isbased upon a type of the task and a temporal characteristic of the task;provide, using the output device, the modified output as a notification;and dismissing the notification upon detection of completion of thetask, the detection of completion being based upon at least one of: acorrelation of a location of the user and the task and transactionaldata from a source other than the electronic device.
 16. The apparatusof claim 15, wherein the instructions executable by the processor toprovide comprises instructions that increase an intensity of thenotification over a period of time.
 17. The apparatus of claim 16,wherein the intensity is increased according to a policy.
 18. Theapparatus of claim 16, wherein the notification comprises a change to adisplayed color.
 19. The apparatus of claim 18, wherein the displayedcolor is displayed on a sub-portion of a display screen.
 20. Theapparatus of 15, wherein the instructions executable by the processor toprovide comprise instructions that relocation of a display screenelement.
 21. The apparatus of claim 15, wherein the instructionsexecutable by the processor to provide comprise instructions that changea size of a display screen element.
 22. The apparatus of claim 15,further comprising instructions that are executable by the processor toprovide the notification on at least one other user device.
 23. Themethod of claim 15, further comprising instructions executable by theprocessor to: detect an event; identify data indicating that the eventhas occurred, wherein said data is not obtained from user input at theelectronic device; and automatically clear the notification based on thedata indicating that the event has occurred.
 24. The apparatus of claim23, wherein the data is selected from the group consisting oftransactional data, web browsing data, and geographic location data. 25.The apparatus of claim 24, wherein the data is geographic location dataobtained from a global positioning satellite (GPS) system.
 26. Theapparatus of claim 23, wherein the notification is a virtualnotification.
 27. A program product, comprising: a computer readablestorage device comprising code executable by a processor, the codecomprising: code that detects, at an electronic device, data associatedwith a notification comprising a reminder related to a task of a user;code that modifies, using a processor, an output based on the data,wherein the modifying comprises modifying an attribute of thenotification based upon the task, wherein the code that modifies isbased upon a type of the task and a temporal characteristic of the task;code that provides, using an output device of the electronic device, themodified output as a notification; and code that dismisses thenotification upon detection of completion of the task, the detection ofcompletion being based upon at least one of: a correlation of a locationof the user and the task and transactional data from a source other thanthe electronic device.